-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Test vanilla event loop windows #180
base: main
Are you sure you want to change the base?
Conversation
Windows can't interrupt the underlying syscall so we have to yield control to the python interpreter to detect ctrl-c once in a while
…till causes problems
…event-loop-windows
…event-loop-windows
…event-loop-windows
@@ -5,6 +5,9 @@ | |||
|
|||
|
|||
@pytest.mark.skipif(sys.version_info >= (3, 13), reason="gevent seems broken on Python 3.13") | |||
@pytest.mark.skipif( | |||
sys.platform == "win32", reason="gevent support broken on Windows, probably due to event loop patching" | |||
) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
tbh, not sure how important gevent support is these days, but maybe there are still libraries making use of it?
I feel I'd rather have synchronicity be on the default event loop implementation to prevent potential inconsistencies of using a different one?
@mwaskom any feedback on this windows-specific (un-)patch? Any idea how prolific gevent usage is these days? |
No idea really. Seems to still get a lot of downloads from PyPI, though that's hard to interpret: https://pypistats.org/packages/gevent |
We have been overriding which event loop implementation to use on windows due to some issues with shutdown emitting junk tracebacks, but with the recent improvements in cancellation synchronization we might have fixed this issue in a better way and could potentially got back to the default event loop on windows.